Sure, you can make it 20 seconds (or any time you want).
Adjust the code to use the long time-format of Lapper, add the seconds and add an extra check to see if seconds have gone above 60.

Maybe you only want the tempo control on certain commands.
That's possible by adding this sub-event:

Then the command you want to check on, should look like this:

Last edited by Yisc[NL], Sat 22 Jul 2023, 17:47.

Add this piece of code to Event OnMSO above this line:

SWITCH( $command )

Add this piece of code to Event OnMSO the after this line:

ENDSWITCH

What kind of commands are you talking about?

Quote from arda556 :

So do you want anything from me?

Bass-Driver, Lapper'ın çalışmayı durdurmasına neden olan gerçek değerlere ihtiyaç duyar. Lapper durduğunda $X_Axis'in değeri nedir? Lapper durduğunda $Y_Axis hangi değere sahip olur? Lapper durduğunda $Z_Axis hangi değere sahip olur? Lapper durduğunda $Heading değeri ne olur? Lapper durduğunda $PLID hangi değere sahip olur? Lapper durduğunda $UCID hangi değere sahip olur?

Bass-Driver needs the actual values that cause Lapper to stop working. What value does $X_Axis have when Lapper stops? What value does $Y_Axis have when Lapper stops? What value does $Z_Axis have when Lapper stops? What value does $Heading have if Lapper stops? What value does $PLID have if Lapper stops? What value does $UCID have if Lapper stops?

Problem has to do with a joinrequest.
Some value is send, that cannot be handled properly by Lapper, which then crashes.
Ofcourse the value should not be able to crash the application, so that has to be investigated by Bass-Driver.
In the mean time you could check what kind of value is send and if there is anything you can do to prevent it from being send or to try and send it in the correct way.

I don't see any use of a counter.
When using a counter, you can add that to the name of the button to give it a dynamic name.
Like this:
The counter should also be used to work out the new top/bottom position of the button.
Like this:


Then the button should be:
When thinking about it, using the counter in the name of the button, could cause trouble, when officials disconnect from the server, so it might be better to use there $userName in the name of the button.

Then the button should be:

The counter can be used to create a unique button name as well as to alter the position of the buttons.
I am not home, so cannot give exact instructions now, but basically it is like this:

OnLapperStart:
- initialise counter and set it to 0

OnConnect event

If connected player is an official:
- raise counter by one
- open button for that official, when counter is 0, top/bottom position are the default value you gave then, when counter is 1, top/bottom position is default value mines 5 (to show the button above the previous button


OnDisconnect event

If disconnected player is an official
- lower counter by one
- close the button of that official

You can do that, but have to give each button a unique name, otherwise they will overwrite each other. You could add the nickname of the officials to the button name, so they always will be unique.

*edit*
Thinking about it, you need to have a counter as well, to keep track of how many officials are connected. Based on that counter you have to change the position of the next button, to avoid them getting on top of each other.

Last edited by Yisc[NL], Wed 12 Jul 2023, 08:01.

That's an easy one, add logging to Lapper when someone connects and write that to the Lapper database.
The next time someone comes on you can either show the last date/time and if none can be found, welcome the player as a new one.

Quote :

No worries. I don't know why they are occasionally falsely detected.

When a new version of an executable goes out, it's not scanned by the populair virus scanners and is therefor detected by them. Once they got the time to scan it and see that it is safe, they will whitelist it and push that to their clients.

Glad to hear it's working.
For future reference, what happens when this is used?

$NewDate = Replace( GetLapperVar(ShortDate,+5),"/","\/");
$NewDate2 = Replace( GetLapperVar(ShortDate),"/","\/");

In most systems \ can be used to escape characters, so this might do the trick here as well.

I am not familiar with Discord, but to me it looks like some character in the message, is misunderstood by Discord, causing the message to get broken. The problem could be with the / which might have to be escaped to get them through. Since I don't know if escaping them is even possible, you might want to try and replace them. Have a go with this:

$NewDate = Replace( GetLapperVar(ShortDate,+5),"/","-");
$NewDate2 = Replace( GetLapperVar(ShortDate),"/","-");

I cannot spot any obvious issue, but am currently not at home to double check things within Lapper.
What happens if you add the following line after the line that is setting $NewDate2?
The line should be: WriteLine( $NewDate2 );
Now a value should be shown on the Lapper console, what is that value?

What is the line (or lines) of Lapper code you have?
It's hard to see what is wrong when we only have a screenshot to go on.
It looks the variable isn't correctly added to the text, but only the actual code can proof that theory.

often questions like this can be answered by reading through the file called Changes.txt
In that file I found this:

In 5 minutes I have put this script together.
There is no close button, but that is on purpose as I think people should be able to code that (there are examples enough to look at).

I've attached the script as a file as well.
Rename the extension to .lpr and make sure to add a reference to addonsused.lpr

Wow, that is more advanced/complicated than I thought off, but on the other end more doable at the same time.
My idea was that !v should cast a vote to end the race and when enough votes would have been given, another layout was loaded.
Your idea is a lot better.

I have given your request a quick try yesterday, but got stuck very early on as I have no idea how the voting system in LFS works and therefor how to program that in Lapper.

Have a look at this thread: https://www.lfs.net/forum/thread/92249

You have to send the data from Lapper to your website.

Lapper cannot connect to a mysql database.
It uses its own local database.

Quote from Viperakecske :

First graphics progress about new lightning and stuff was in 2018... soon 5y ago and yet no public version

So, what is your point?
If you don't like it here, you are free to leave.
Apparantly you did something wrong in the past and are proud to show that in your profile picture.
You have a new account and are still b*tching about the game at every possible moment.
Be pleased with you have and enjoy that or go and do something else and maybe check in once or twice a year.
Scawen only wants to deliver things at the highest quality possible and has proven that over and over again.
Let the guy do what he does best and at some point another gem comes out of the back.

Quote from HeRRC :

I remember that last night we were on the server testing mods and some of the participants had problems with the download, is it because of that?
they usually take a long time, but sometimes it's several minutes.

Maybe this can be improved as we could improve the servers in Brazil that are not good for big events...

It has already been improved, well Scawen and Victor made an attempt at a fix.
See the below option and give that a try:

If you enable Options... Misc - Allow HTTP redirect [EXPERIMENTAL]

Quote from Scawen :

How it relates to E-Challenge: on this thread there are some scripts designed to make it easy to set pit instructions to change tyres, when conditions change to wet or dry.

Is there a hidden wet condition in LFS?